Add headshots and update research areas for three lab members - #5

Quinn McIver's research area now reads "Certification-Driven Conceptual Design Optimization for Regional Air Mobility Aircraft", and Khushi Piparava's reads "Multi-fidelity reduced order models". Eden Enwiya gains an "Aircraft visualization" area. All three get LinkedIn links, and Khushi and Eden get headshots in place of the placeholder avatar.

Quinn's replacement headshot arrived as a 10 MB 4982x7474 portrait named with an uppercase .JPG extension. The extension is lowercased because CI is case-sensitive and _config.yml only lists lowercase .jpg under imagemagick.input_formats, so the uppercase name would have broken the image and skipped WebP generation. The image is cropped square anchored near the top -- .person-photo crops to a centered square, which would otherwise cut through the forehead -- then resized to 1500x1500 to match the other headshots.

Summary

Describe what changed and why.

Adding your site to the showcase? We no longer accept pull requests for that. Please close this PR and post a request in the Showcase category of GitHub Discussions instead — entries are reviewed and added periodically.

Ownership Routing

• I confirmed this PR targets the correct repo based on docs/BOUNDARIES.md.
• This PR only changes starter-owned scope (al-folio) or I am porting a routed change and linked the owning repo issue/PR.

Owning repo (if not starter):
Related issue/PR:

Plugin Ecosystem (if applicable)

• Not applicable
• This PR proposes a plugin for featured-only listing.
• This PR proposes a plugin for bundled starter inclusion.

If plugin-related, provide:

• Plugin repo URL:
• Gem name:
• Jekyll plugin id:
• Compatibility (al_folio_min/al_folio_max):
• Demo page/post path:
• Maintainer contact:

Starter Wiring Changes

• Not applicable
• Updated Gemfile dependency wiring.
• Updated _config.yml plugin activation/config.
• Updated _data/featured_plugins.yml metadata.

Validation

• npm ci
• bundle exec jekyll build
• npm run lint:prettier
• npm run lint:style-contract
• Integration tests (test/integration_*.sh) as needed
• Visual tests (npm run test:visual) as needed

Notes

Compatibility, migration implications, and follow-ups: